Skip to content

feat(compare): add MiniMax M3 to compare model registry#451

Closed
functionstackx wants to merge 1 commit into
masterfrom
fix/compare-minimax-m3
Closed

feat(compare): add MiniMax M3 to compare model registry#451
functionstackx wants to merge 1 commit into
masterfrom
fix/compare-minimax-m3

Conversation

@functionstackx

@functionstackx functionstackx commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

MiniMax M3 was added to the dashboard model dropdown (#444, ordering in #450) but never to COMPARE_MODEL_SLUGS in packages/app/src/lib/compare-slug.ts — the hand-maintained registry that drives /compare, /compare-per-dollar, the sitemap, and their OG images. So M3 was absent from all compare surfaces. (/about needed no change — it derives from DB_MODEL_TO_DISPLAY and already lists MiniMax-M3.)

Changes

  • compare-slug.ts: add minimax-m3 entry (displayName: 'MiniMax-M3', dbKeys: ['minimaxm3'], label MiniMax M3 428B), placed before minimax-m27 so the newer flagship leads within the family, mirroring DeepSeek V4 Pro before R1. The bare minimax alias stays on minimax-m27 for backward compat (same pattern as deepseekdeepseek-r1). M3 is a distinct 428B architecture, not an M2 point release, so it gets its own slug rather than joining the M2 dbKey group.
  • compare-ssr.ts: add 'MiniMax-M3' to KNOWN_MODELS so ?g_model= URL overrides validate.
  • compare-slug.test.ts: new tests for parsing minimax-m3-h100-vs-h200 and slug/alias resolution; the existing round-trip suites cover the new entry automatically (34 tests pass).
  • docs/adding-entities.md: add the compare-slug registry and KNOWN_MODELS steps to the Adding a New Model checklist — they weren't listed, which is why M3 fell through.

Notes

  • Only B300 currently has minimaxm3 benchmark rows (verified against the live availability API), so the /compare index won't render an M3 section until a second GPU has data — getComparablePairsByModelSlug requires both sides of a pair. The section, sitemap URLs, and OG images appear automatically once that happens; direct /compare/minimax-m3-* URLs render the standard empty state until then.
  • Overlay support: not applicable — this changes the SSR compare-page model registry only, no inference/evaluation chart data paths.

🤖 Generated with Claude Code


Note

Low Risk
Registry and documentation-only changes to compare URL/metadata; no auth, ingest, or inference paths.

Overview
MiniMax M3 is wired into the hand-maintained compare registry so it can appear on /compare, /compare-per-dollar, sitemaps, and OG images—surfaces that do not follow MODEL_CONFIG from the dashboard.

A new minimax-m3 entry in COMPARE_MODEL_SLUGS uses dbKeys: ['minimaxm3'], sits before minimax-m27 (newer flagship first), and keeps the bare minimax alias on the M2 series for backward compatibility. MiniMax-M3 is added to KNOWN_MODELS so ?g_model= overrides validate on compare SSR pages.

Tests cover parsing minimax-m3-* URLs and slug resolution. docs/adding-entities.md now lists compare-slug.ts and compare-ssr.ts in the “add a model” checklist so future models don’t miss compare registration.

Reviewed by Cursor Bugbot for commit fd63b9c. Bugbot is set up for automated code reviews on this repo. Configure here.

@functionstackx functionstackx requested a review from adibarra as a code owner June 13, 2026 00:25
@vercel

vercel Bot commented Jun 13, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
inferencemax-app Ready Ready Preview, Comment Jun 13, 2026 6:45pm

Request Review

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant